Isolate endpoint - Crowdstrike

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Content Index

When a new Microsoft Sentinel incident is created, this playbook gets triggered and performs below actions:

Attribute Value
Type Playbook
Solution CrowdStrike Falcon Endpoint Protection
Source View on GitHub

Additional Documentation

📄 Source: CrowdStrike_ContainHost/readme.md

Crowdstrike ContainHost

## Summary When a new Microsoft Sentinel incident is created, this playbook gets triggered and performs below actions: 1. Fetches the device information from Crowdstrike 2. Contain host if it is not already contained 3. Enrich the incident with device information from Crowdstrike Comment example

  1. Close the incident if contained the host

Crowdstrike_ContainHost

Prerequisites

  1. Azure Key vault is required for storing the Crowdstrike ClientID and Secrets, create key vault if not exists learn how
  2. Add Crowdstrike Client ID and Client Secret in Key vault secrets and capture the keys which are required during the template deployment
  3. CrowdStrike_Base playbook needs to be deployed prior to the deployment of this playbook under the same subscription and under the same resource group.
  4. CrowdStrike_Base playbook needs to be added in the access policy of the Key Vault learn how

Deployment instructions

  1. Deploy the playbook by clicking on "Deploy to Azure" button. This will take you to deploying an ARM Template wizard.

Deploy to Azure Deploy to Azure

  1. Fill in the required parameters:
    • Playbook_Name: Enter the playbook name here (Ex:Crowdstrike_ContainHost)
    • CrowdStrike_Base_Playbook_Name : Enter the base playbook name here (Ex:CrowdStrike_Base)

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, you will need to authorize connections. 1. Click the Microsoft Sentinel connection resource 2. Click edit API connection 3. Click Authorize 4. Sign in 5. Click Save

b. Configurations in Sentinel

  1. In Microsoft sentinel analytical rules should be configured to trigger an incident with risky device
  2. Configure the automation rules to trigger this playbook

Playbook steps explained

When Microsoft Sentinel incident creation rule is triggered

Microsoft Sentinel incident is created. The playbook receives the incident as the input.

Entities - Get Hosts

Get the list of risky devices as entities from the Incident

Initialize variable comment

Initialize a string variable to hold comments to update in the incident

Initialize variable success from crowdstrike

Initialize a string variable to hold the success or failure information from crowdstrike api actions

CrowdStrike Base

Call the base logic App to get access token and Falcon Host URL

HTTP - Get device id

This gets the device id from crowdstrike filtered by hostname

Parse JSON Get device id response

This prepares Json message for the device id response

### Condition to check if device is present in crowdstrike 1. If device is present, get the device information from crowdstrike API and prepares HTML table with required information 2. Checks the device status, if not contained/normal the playbook will contain the device

### Compose image to add in the incident This action will compose the Crowdstrike image to add to the incident comments

Add a comment to the incident with the information

This action will enrich the incident with the constructed HTML table with device information

Condition to check if playbook contained the device

If playbook contained the device, then close the incident with proper closure comments

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Playbooks · Back to CrowdStrike Falcon Endpoint Protection